… output (v3.5.3)

A component that updated its own state during render (the derived-state pattern,
if x { setState(...) }) stored the new value and scheduled a commit, but the
component was never re-run — so the committed DOM showed a value the component had
not actually rendered (rendered 0, DOM showed 1) and never converged.

renderFunctionComponent now detects a render-phase update via a new
Runtime.activeRenderFiber flag (set only around the actual render call, distinct
from the ambient currentFiber so the SSR path and hook unit tests that set
currentFiber manually are unaffected) and re-runs the component to convergence,
bounded at 25 iterations with a diagnostic to guard an unconditional-setState
infinite loop. Matches React's "keeps restarting until there are no more new
updates."

The hook setter, when its owner == activeRenderFiber, marks the fiber
renderPhaseUpdate and returns without scheduling (the convergence loop handles
re-render). Found bug-hunting GWC's state management against React. Covered by
TestRenderPhaseUpdateConverges / DerivedStateOneStep / UnconditionalDoesNotHang;
full suite + native/wasm pass, no regression.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>